home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970626-19970929
/
000290_news@newsmaster….columbia.edu _Wed Sep 3 19:18:25 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id TAA29783
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 3 Sep 1997 19:18:24 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id TAA01775
for kermit.misc@watsun; Wed, 3 Sep 1997 19:18:23 -0400 (EDT)
Path: news.columbia.edu!panix!logbridge.uoregon.edu!europa.clark.net!4.1.16.34!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MSKermit 3.14 problem
Message-ID: <DdRi9ZsOl67n@cc.usu.edu>
Date: 3 Sep 97 14:26:52 MDT
References: <01bcb7cc$b2b132e0$LocalHost@ivan> <5uk51l$lq3$1@apakabar.cc.columbia.edu>
Organization: Utah State University
Lines: 35
Xref: news.columbia.edu comp.protocols.kermit.misc:7610
In article <5uk51l$lq3$1@apakabar.cc.columbia.edu>, fdc@watsun.cc.columbia.edu (Frank da Cruz) writes:
> In article <EFwrDC.Mt5@freenet.buffalo.edu>,
> L. Chen <am302@freenet.buffalo.edu> wrote:
> : On 2 Sep 1997, Frank da Cruz wrote:
> : > Then read the NETWORKS\SETUP.DOC file. It explains everything you need to
> : > do to set up MS-DOS Kermit to make TCP/IP connections.
> :
> : Can 3.14 make tcp/ip connections in Win95 ?
> :
> MS-DOS 3.14 is not, and can not be, a Winsock client. The only way it could
> make TCP/IP connections is through its own built-in TCP/IP stack or through
> its BIOS interface. Setting this up is not for the feint of heart, and in
> any case is not recommended or supported.
>
> - Frank
--------
Amplifying this a bit because my place does use MSK heavily in
Win95...
MSK is a DOS program, a real mode affair, not a Windows-only item.
It can use its internal TCP/IP stack to a Packet Driver or a real-mode
Novell ODI driver. It does not communicate directly with protected mode
lan drivers nor directly with NDIS of any flavor.
What we do is use Novell's real mode ODI material (lan driver, and
VLMs). To operate MSK this way within a Windows DOS box one needs shim WINPKT,
and that in turn needs a Packet Driver beneath it. ODIPKT is that PD beneath
it. Thus the drill is to load ODI components as usual, load ODIPKT, load
WINPKT, start Windows.
There is a rule of only one TCP/IP stack using a lan adapter at the
same time. Thus you can't add MS' TCP/IP stack and winsock at the same time
as MSK is using its own TCP/IP stack. You can use Novell's real mode TCP/IP
stack and its matching winsock, but not at the same time as MSK is running.
We load Novell's stack when needed, and unload it when not needed. The
winsock interface provided is the 16-bit variety.
These items are discussed in the MSK release documentation.
Joe D.